Server-side resource prioritization

ABSTRACT

A process for prioritizing content responses executed by a first server in a distributed cloud platform. The first server including processor, and a non-transitory machine-readable storage medium that provides instructions that, when executed by the processor, causes the first server to perform operations including to receive, at a proxy server, a request for a plurality of content items from a client device, where the proxy server is in a distributed cloud computing platform, to receive at least one of the plurality of content items from an origin server or a cache, to determine a priority scheme for ordering the plurality of content items, where the priority scheme differs from a priority scheme of the client device and differs from a priority scheme of a domain of the plurality of content items, and to send a response including the plurality of content items to the client device in an order according to the priority determined scheme.

FIELD

Embodiments of the invention relate to the field of network computing;and more specifically, to a proxy server that prioritizes streaming aresource to at least one requesting client device while the resource isbeing received at the proxy server is described.

BACKGROUND

Web browsers and similar client applications that run at client devicesaccess network resources by making hypertext transfer protocol (HTTP)requests that are directed to an origin server. With SPDY, HTTP/2 andQUIC web request protocols, the client applications make requests ofnetwork resources provided by the origin server and specifies how theresponses should be delivered (in what order and how to split bandwidthbetween them). However, the specified prioritization of the responsesvaries by the client application. The specified prioritization of theclient applications is not consistent and are not based on anyinformation about the requested network resources that enables theprioritization to be an optimal user experience or use of bandwidth.

The prioritization of requested content items that make up a networkresource must be supported at the origin server to be implemented.Generally, the origin servers that support the SPDY, HTTP/2 and QUICprioritization attempt to honor the prioritization (e.g., in terms ofdependencies and weights) that the client applications specify. Goodprioritization is critical to the user experience, particularly onslower connections where the difference between good and badprioritization can be tens of seconds to minutes of a blank screenbefore seeing the requested content load. However, many clientapplications like web browsers have poorly constructed prioritizationschemes or lack any support for prioritization. Those clientapplications that do support prioritization provide a genericprioritization strategy that will not be optimal for all applicationsand conditions.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may best be understood by referring to the followingdescription and accompanying drawings that are used to illustrateembodiments of the invention. In the drawings:

FIG. 1 is a sequence diagram that illustrates exemplary operations for aproxy server receiving a set of requests for a network resource and theconstituent content items and the prioritization of responses with therequested content items according to an embodiment.

FIG. 2 is a flow diagram that illustrates exemplary operations for aproxy server handling a request from a client devices and prioritizingcontent items for a response to the request to the client deviceaccording to an embodiment.

FIG. 3 is a flow diagram that illustrates exemplary operations forprioritizing content items for a response to the client device.

FIG. 4 is a block diagram illustrating an example prioritization schemeof the prioritization module.

FIG. 5 is a block diagram illustrating another example prioritizationscheme of the prioritization module.

FIG. 6 is a block diagram illustrating another example prioritizationscheme of the prioritization module.

FIG. 7 is a block diagram of one example of the proxy serverarchitecture in which the prioritization module is executed according toone embodiment.

DESCRIPTION OF EMBODIMENTS

A method and apparatus for a proxy server to prioritize content items ofa network resource returned in a set of responses to a set of requestsfrom a client device for the network server. The proxy server receives arequest for a network device (e.g., a web page) from a first clientdevice. The request may be, for an example, an HTTP/S request for a webpage, web application or similar network resource. For instance, therequested network resource could be a web page with scripts, images,audio and similar related files. The proxy server determines whether thenetwork resource is fully available in a local cache that is availableto the proxy server. Where the network resource is not fully availablein the local cache, the proxy server transmits a set of requests for thenetwork resource to another server (e.g., the origin server) and beginsreceiving the content items associated with the network resource. Whilethe network resource is being received, the proxy server sends responsesto the requesting client device without waiting for all of the contentitems of the network resource to be fully received at the proxy server.The proxy server however can alter the order (i.e., re-prioritize) thecontent items being sent to the requesting client device. Thus, theproxy server can implement a prioritization scheme that improves thethroughput and responsiveness between the proxy server and the clientdevice for key content items to reduce their load times and improve userexperience.

FIG. 1 is a sequence diagram that illustrates exemplary operations for aproxy server that provides a prioritization module to manage the orderof content item responses for client devices while the resource is beingreceived at the proxy server according to an embodiment. The diagramincludes a client device 110 that is communicatively connected to theproxy server 120. Each client device 110 is a computing device (e.g.,laptop, workstation, smartphone, mobile phone, tablet, gaming system,set top box, wearable device, Internet of Things (IoT) device, etc.)that is capable of transmitting and/or receiving network traffic. Eachclient device may execute a client network application such as a webbrowser, native application, or other application that can accessnetwork resources (e.g., web pages) that are associated with or includea set of content items (e.g., images, word processing documents, PDFfiles, movie files, music files, or other computer files). In theexample embodiment of FIG. 1, a single client device and proxy serverare illustrated for sake of clarity and conciseness. However, oneskilled in the art would understand that a proxy server can service anynumber of client devices and that any number of proxy servers may bepresent in a network such as a distributed to service network resourcerequests.

The proxy server 120 is a physical server that is configured to retrievea network resource to requesting client devices as will be described ingreater detail herein. The proxy server 120 has a multi-processorarchitecture where each request may be handled by a different processand/or potentially on a different processor. The proxy server 120includes a request processing module 150 that includes a set of requestprocess 115. A ‘set,’ as used herein refers to any whole number of itemsincluding one item. The request processing module 150 may be acting as areverse proxy web server with caching. Each request process 115processes one or more requests. The request process 115 may be executedon any processor or core available to the proxy server. Although asingle request processes is illustrated, there may be more requestprocesses being executed on the proxy server 120. Each request process115 can process multiple requests concurrently. The proxy server 120 canalso include a memory structure that can be a shared memory that isavailable to each of the request processes 115. The memory structureincludes non-transitory computer readable media for storing data andinstructions. In some embodiments, the memory structure can include acache for content items and related data about the cached content items.The cache can be utilized to store previously retrieved content itemssuch that the request processing module does not have to request thesecontent items from an origin server 140 on subsequent requests fromclient devices. The cache is communicatively available to the proxyserver. The cache can be included within the proxy server 120 or may bephysically separate from the proxy server. If physically separate, thecache is available to the proxy server 120 and is typically part of thesame colocation site. That is, it is generally faster to retrieve filesfrom the cache instead of from the origin server 140.

Although not illustrated in FIG. 1, the proxy server 120 may be part ofa distributed cloud computing network that includes multiple proxyservers that are geographically distributed. The proxy servers may be indifferent points-of-presences (PoPs). Each PoP may include one or morephysical servers (e.g., one or more proxy servers, one or more controlservers, one or more domain name service (DNS) servers (e.g., one ormore authoritative name servers, one or more proxy DNS servers), and oneor more other pieces of network equipment such as router(s), switch(es),and/or hub(s)). Each PoP may be part of a different data center and/orcolocation site. The distributed cloud computing network may providedifferent services for customers (e.g., domain owners or operators) suchas protecting against internet-based threats, performance services(e.g., acting as a content delivery network (CDN) and dynamicallycaching customer's files closer to visitors, pageacceleration/optimization), TCP stack optimizations, and/or otherservices. Although not illustrated in FIG. 1, there are other physicaldevices between the proxy server 120 and the client devices such asrouters, switches, and similar network and computing devices.

The origin server 140, which may be owned or operated directly orindirectly by a third-party to the distributed cloud computing network,is a computing device on which a network resource resides and/ororiginates (e.g., web pages) that have an associated set of contentitems 135) (e.g., images, word processing documents, PDF files moviefiles, music files, or other computer files). The origin server 140 canservice requests for these content items. The content items may beassociated with a domain, where the domain is a network of commonlyadministered computers or devices typically having an associated domainname. The origin server 140 can service multiple domains. The originserver 140 can be any type of computing device (e.g., server, cloudcomputing platform or similar computing devices) and have any type ofdata storage system to store the content items.

The proxy server 120 may operate as a reverse proxy and receive requestsfor network resources (e.g., HTTP requests) of a domain of the originserver 140. In an embodiment where the proxy server 120 is one ofmultiple proxy servers that are part of a distributed cloud computingnetwork, the proxy server 120 may receive a request from a particularclient device as determined by the network infrastructure according toan Anycast implementation or by a geographical load balancer. Forinstance, each of the proxy servers may have a same anycast IP addressfor a domain of the origin server 140. If the origin server 140 handlesthe domain “example.com,” a DNS request for “example.com” returns anaddress record having the anycast IP address of the proxy servers. Whichone of the proxy servers receives and handles a request from a clientdevice depends on which proxy server is closest to the client device interms of routing protocol configuration (e.g., Border Gateway Protocol(BGP) configuration) according to an anycast implementation asdetermined by the network infrastructure (e.g., router(s), switch(es),and/or other network equipment between the requesting client and theproxy servers). In some embodiments, instead of using an anycastmechanism, a geographical load balancer is used to route traffic to thenearest proxy server.

In an embodiment, the proxy server 120 receives a request for a networkresource of a domain of the origin server 140 because the DNS record(s)for that domain are changed such that DNS records of hostnames of thedomain point to an IP address of the proxy server instead of the originserver 140. In some embodiments, the authoritative name server of thethird-party domain is changed to an authoritative name server of thedistributed cloud computing network and/or individual DNS records arechanged to point to the proxy server 120 (or point to other domain(s)that point to the proxy server 120). For example, the domain owners maychange their DNS records to point to a CNAME record that points to theproxy server 120.

FIG. 2 is a flowchart illustrating a process for providing prioritizedresponses to network resource requests in one embodiment. At operation201, the proxy server receives a request for a network resourceassociated with a set of content items. For example, referencing FIG. 1,the proxy server 120 receives a request for a content item 135 of adomain of the origin server 140 from the client device 110. Forinstance, the request may be an HTTP/S GET request. In the example ofFIG. 1, the request is for a network resource that includes the contentitem 135. The requested content item can be any type of content item(e.g., images, audio, applications or similar content items). Therequest is processed by a first request process 115 of the proxy server120. For example, the request from the client device 110 is processed bythe request process 115. In an embodiment, the proxy server 120 receivesthe request because a DNS request for the hostname returns an IP addressof the proxy server 120 instead of the origin server 140.

Next, at operation 203, the request process or similar process of theproxy server 120 determines whether the content item 135 is available inthe cache. If the content item is not available in the cache, the proxyserver 120 transmits a request for the file to the origin server 140.This request may be an HTTP/S GET request and be similar to the requestreceived in operation 1. In the example of FIG. 1, this request is forthe content item 135. Although FIG. 1 shows the proxy server 120transmitting the request for the content item to the origin server 140,in another embodiment the proxy server 120 transmits the request for thefile to a different server (e.g., a different proxy server that may havethe file cached).

At operation 205, the proxy server 120 receives a response from theorigin server 140 or is able to retrieve the content item from thecache. The amount of time necessary to receive the content item 135 fromthe origin server 140 depends, in part, on the size of the content item135 and the available transmission bandwidth. At operation 207, as thecontent item is being received from the origin server 140 or from thecache, the proxy server 120 determines the type of the content item andany related content items that are part of a request for a networkresource. For example, if the requested network resource was a web page,then the retrieved content items can include the HTML file of the webpage, images of the web page, and similar content items.

At operation 209, the prioritization module at the proxy serverdetermine an order or priority of the content items to be returned tothe client device. The operation of the prioritization module todetermine the order of the content items is discussed further hereinbelow with reference to FIGS. 3-6. The prioritization module canre-order the content items retrieved from the cache and the originserver from a default order that can be set by the client device (e.g.,a browser can request a specific prioritization), the origin server, orthe default configuration of the requested network resource. Theprioritization module can re-order the individual bytes of the contentitems in addition to the content items as a whole. For example, multipleimages can be interleaved or higher priority content items or portionsthereof can be inserted into a response stream during transmission oflower priority content items.

At operation 211, the request processing module and request processforward the content items to the client device as a set of re-orderedresponses according to the prioritization scheme determined by theprioritization module. The prioritization module can thereby improve thespeed and quality of the user experience in accessing the requestednetwork resource as further discussed herein below.

FIG. 3 is a flow diagram that illustrates exemplary operations of aprioritization module for a proxy server to re-order the content itemsto requesting client devices according to an embodiment. The operationsof FIG. 3 will be described with respect to HTTP/S request andresponses. But, the operations of FIG. 3 can be performed with differenttypes of requests and responses such as QUIC requests and response. Inan embodiment, the first server referred to in FIG. 3 is the proxyserver 120 and the second server referred to in FIG. 3 is the originserver 140.

This process is a part of the operation 209 described above withreference to FIG. 2, where the prioritization module is handling a setof content items and a set of responses to a request from a clientdevice. A first server receives a first request for a file from a firstclient device. The requested file may be relatively large (e.g., greaterthan 500 MB). The request may be an HTTP/S request. The request is for afile of a domain handled by a second server (e.g., an origin server).That is, the file does not originate from the first server.

At operation 301, the prioritization module determines the priorityinformation of the browser or similar client device-based prioritizationinformation. Browser implementations of HTTP/2, QUIC and similarprioritization vary significantly and (wen in the best cases are stillnot optimal. HTTP/2 and QUIC do not enforce browser prioritization inany way and thus the browser prioritization can be treated as asuggestion from the client device on content item delivery order.Delivering content items in an optimal order can have a significantimpact on the user experience such as the performance of browser loadinga page. Making the prioritization programmable on the server-sideprovides significant benefits. Browsers with poor prioritization schemescan have their prioritization over-ridden and content items can bedelivered in an optimal order even with no client support. Browsers withgood or reasonable prioritization schemes but with gaps or issues can beimproved (e.g., allowing for images to download concurrently where thebrowser fails to enable this behavior). Cases where a specificapplication is not optimal with a “default” prioritization scheme can beimproved on an application-by-application basis.

At operation 303, the prioritization module determines theprioritization information of a specific client device request. This caninclude the prioritization information specified in the request itselfthat may be based on request protocol or similar factors. As the contentitems are returned by the cache or origin server, the prioritizationmodule can examine the content items to determine if they includeinformation related to prioritization, at operation 305. The contentitems can include information about their type or similar informationthat is collected to assist in the re-ordering of the content items fordelivery to the client device. In addition, a domain of the contentitems can include specific prioritization scheme information where thedomain attempts to manage the prioritization of the responses for thecontent items.

At operation 307, if there was not any priority information from thedomain of the content items handled be the origin server, then theprioritization module determines a prioritization scheme that is basedon the configured prioritization scheme of the proxy server that can bemodified in some cases to accommodate some priority preferences from theclient device (e.g., from the browser). At operation 309, if there ispriority information for the domain of the content item provided by theorigin server, then the prioritization module determines aprioritization scheme that is based on the configured prioritizationscheme of the proxy server that can be modified in some cases toaccommodate some priority preferences from the client device (e.g., fromthe browser) as well as the prioritization scheme of the domain. Atoperation 311, the prioritization module re-orders the content items andorders them into a set of responses to be sent to the client deviceaccording to the prioritization scheme determined at operations 307 or309.

The prioritization module can be configured to accommodate a wide rangeof priority schemes that can be configured by domain administrators orother entities. In some embodiments, rather than administratorconfiguration of the priority scheme, machine learning, or similarmechanisms can be utilized to determine optimal prioritization forindividual pages. The prioritization module can also observe the contentitems they are returned from the origin server and sent to the clientdevices to track performance and inform the prioritization of futurerequests. Client devices can also provide feedback on the efficacy ofthe prioritization schemes to enable further optimization of theprioritization scheme.

The embodiments of the prioritization module improve performance anduser experience in accessing network service (e.g., in HTTP/2 and QUIC)by using a prioritization strategy, driven by the proxy server, ratherthan the current approach of using a prioritization based on browserassumptions. Proxy (e.g., edge device) driven prioritization can followa standard provider defined structure by default or can be fine-tuned bycustomers for their individual network resources (e.g., web pages andcontent items).

The operations of the proximity module in developing a priority schemecan support site-specific (i.e., domain specific) logic. Customers oradministrators can determine priority ordering independent of browsersupport and without relying on additional technology such as priorityhints to be implemented by network resource request technologies. Insome embodiments, advanced features can be built on top of the custompriority support provided by the prioritization module includinglearning the optimal priority for individual pages and changing prioritymid-stream for progressive images (allowing for server-side imagestreaming).

The prioritization module can support modifying the prioritization of agiven request including enabling the re-ordering of requests, specifyingconcurrency of download for requests (e.g., exclusive, shared sequentialor shared concurrent), and providing a mechanism to dynamically changethe priority of an in-flight response at various byte offsets in thefile (e.g., progressive image delivery).

FIG. 4 is a diagram illustrating a first example prioritization scheme.In the illustrated example, a priority scheme can be provided by theprioritization module where the sequencing of content items in responsescan be handled by classifying each content item request with a prioritylevel from 0-255 (e.g., with 255 being highest priority). Requests at ahigher priority are delivered before requests at a lower priority (withno concurrency crossing priority boundaries). In the illustratedexample, responses have priority 255 and 119. Requests at the samepriority level are delivered in the order they are requested (e.g., thestream identifier can be increased in order of the requests, deliveringthem in order of stream identifier). Strictly using priority levelswould not allow for controlling the concurrency of requests so theprioritization scheme can also include another parameter for thepriority of each request (e.g., concurrency (0, 1 or n)). Requests witha concurrency of 0 are delivered first at a given priority level andwithout sharing bandwidth with any other requests. This is optimal forthings like blocking scripts and CSS.

In this first example prioritization scheme, requests with a concurrencyof 1 are grouped together and delivered sequentially within the group.The group as a whole splits bandwidth evenly with the requests withconcurrency n. (i.e., 50% to the one resource at a time in theconcurrency 1 group and 50% to the n-concurrency group). This is optimalfor things like async or deferred scripts where it is desirable for userexperience to load them quickly but not exclusively and where they areoptimally delivered completely and in order. Requests with a concurrencyn are grouped together in a single group (regardless of each request'sconcurrency).

In one embodiment, the bandwidth is split evenly across all requests inthe group. Bandwidth splitting is done at a frame-by-frame level wherethe next frame to be sent is evaluated as every frame of data is beingprepared to be sent (assuming the data streams are chunked in aconfigurable frame size for processing). In one embodiment, theprioritization scheme (1) only considers responses where data isavailable to be sent, (2) selects from the responses with the highestpriority level, (3) where “concurrency 0” responses are available, theprocess fills the frame with the “concurrency 0” response that wasrequested earliest (i.e., the lowest stream identifier for HTTP/2), (4)otherwise, the process can utilize a round robin between the“concurrency, 1” and “concurrency n” groups, picking one frame from eachgroup. Within the “Concurrency 1” group (5), the process fills the framewith the response that was requested earliest (i.e the lowest streamidentifier for HTTP/2). Within the “concurrency n” group (6), theprocess utilizes a round robin across all of the available responses.

The first example prioritization scheme assumes that the priorityinformation will be available at the start of a response (i.e., in aresponse header) so dynamically adjusting the priority mid-response canbe managed in a way that it can be done automatically. This can beachieved by providing a list of byte offsets and new priority levels. Aseach frame is sent the byte offset is checked and if it crossed aspecified threshold the priority of the request will be changed to thenew priority level. In other embodiments the concurrency could also beadjusted for completeness. The main use case for this embodiment isprogressive image delivery where the initial scans of an image aredelivered first and then the priority for the final scans are deliveredafter other images have completed.

FIG. 5 is a diagram of a second example prioritization scheme accordingto one embodiment. In this example prioritization scheme, a requestheader for inbound requests is added with the current HTTP/2 or QUICinformation (weight, exclusive). For cases where the parent stream is aplaceholder stream for grouping, the process also provides the parentstream identifier and weight (as a “group”). This is informational fordownstream processing and can be used for identifying things likeimportant scripts vs async scripts. For example, this information can berepresented as, cf-request-priority: weight=192; exclusive=1, orcf-request-priority: weight=192; exclusive=0; group=3; group-weight=127.

The second example prioritization scheme can map the existing HTTP/2priorities to the new priorities using a “default prioritization,” Thesecond example prioritization scheme can add support for a responseheader to specify the priority level and concurrency separated by aslash cf-priority: 255/0, cf-priority: 119/1, cf-priority: 119/n). Thesecond example prioritization scheme can add support for a separateresponse header that specifies priority changes at specific byteoffsets. The priority changes can be a comma-separated list in theformat <bytes>:<priority>/<concurrency>, For example,cf-priority-change: 10240:52/n,20480:24:1.

The second example prioritization scheme includes a defaultprioritization. Mixing and matching the existing HTTP/2 prioritizationwith the second example prioritization scheme can lead to issues withmixing responses from both prioritization schemes. The performance andconsistency can be optimized with clear default priorities such thatcustomers and developers can prioritize their explicit responsesaccordingly.

The proxy server can maintain a basic mapping of mime type topriority/concurrency if explicit prioritization isn't provided throughresponse headers. For example, FIG. 5 illustrates an example ofprioritization defaults for the Chrome browser.

The proxy server can also support a logic layer that provides additionsdefaults using browser-specific heuristics (e.g., in a first-partyworker that runs on all requests). The basic mappings can be the same,but the logic can also include prioritization tweaks for visible images,critical scripts, and similar content items using the inbound priorityinformation from the browsers as available (e.g., the Chrome and Firefoxbrowsers). FIG. 6 illustrates the more detailed mapping supported by thelogic layer.

The prioritization will be affected by the prioritization module whenthe response headers are available, so the content type can be detected(if specified) and the requested HTTP/2 prioritization information canbe leveraged. By default, the responses can be prioritized based oncontent type. In some cases, for well-known browser engines that providecontent-specific weights the priorities can be adjusted. For example,the Chrome browser sets the exclusive bit and assigns the weight basedon the internal priority, the Safari browser maps the internalpriorities to weights, and the Firefox browser uses the phantomleader/follower groupings.

FIG. 7 illustrates a block diagram for an exemplary data processingsystem 700 that may be used in some embodiments. Data processing system700 includes one or more processors 705 and connected system components(e.g., multiple connected chips). One or more such data processingsystems 700 may be utilized to implement the embodiments and operationsdescribed with respect to the proxy server, or other electronic device.

The data processing system 700 is an electronic device which stores andtransmits (internally and/or with other electronic devices over anetwork) code (which is composed of software instructions and which issometimes referred to as computer program code or a computer program)and/or data using machine-readable media (also called computer-readablemedia), such as machine-readable storage media 710 (e.g., magneticdisks, optical disks, read only memory (ROM), flash memory devices,phase change memory) and machine-readable transmission media (alsocalled a carrier) (e.g., electrical, optical, radio, acoustical or otherform of propagated signals—such as carrier waves, infrared signals),which is coupled to the processor(s) 705. For example, the depictedmachine-readable storage media 710 may store program code 730 that, whenexecuted by the processor(s) 705, causes the data processing system 700to execute the prioritization module 130.

The data processing system 700 also includes one or more input or output(“I/O”) devices and interfaces 725, which are provided to allow a userto provide input to, receive output from, and otherwise transfer data toand from the system. These I/O devices 725 may include a mouse, keypad,keyboard, a touch panel or a multi-touch input panel, camera, framegrabber, optical scanner, an audio input/output subsystem (which mayinclude a microphone and/or a speaker), other known I/O devices or acombination of such I/O devices. The I/O devices and interfaces 725 mayinclude wireless transceivers, such as an IEEE 802.11 transceiver, aninfrared transceiver, a Bluetooth transceiver, a wireless cellulartelephony transceiver (e.g., 2G, 3G, 7G, 5G), an NFC transceiver, oranother wireless protocol to connect the data processing system 700 withanother device, external component, or a network and receive storedinstructions, data, tokens, etc. For instance, a wired or wirelesstransceiver may transmit and receive messages to and from the proxyserver as described herein.

Additional components, not shown, may also be part of the system 700,and, in certain embodiments, fewer components than that shown in FIG. 7may also be used in a data processing system 700. One or more buses maybe used to interconnect the various components shown in FIG. 7.

Thus, an electronic device (e.g., a proxy server) includes hardware andsoftware, such as a set of one or more processors coupled to one or moremachine-readable storage media to store code for execution on the set ofprocessors and/or to store data. For instance, an electronic device mayinclude non-volatile memory containing the code since the non-volatilememory can persist the code even when the electronic device is turnedoff, and while the electronic device is turned on that part of the codethat is to be executed by the processor(s) of that electronic device iscopied from the slower non-volatile memory into volatile memory (e.g.,dynamic random access memory (DRAM), static random access memory (SRAM))of that electronic device. Typical electronic devices also include a setor one or more physical network interface(s) to establish networkconnections (to transmit and/or receive code and/or data usingpropagating signals) with other electronic devices. One or more parts ofan embodiment of the invention may be implemented using differentcombinations of software, firmware, and/or hardware.

The techniques shown in the figures can be implemented using code anddata stored and executed on one or more computing devices (e.g., clientdevice, proxy server, origin server, etc.). Such computing devices storeand communicate (internally and/or with other computing devices over anetwork) code and data using machine-readable media, such asnon-transitory machine-readable storage media (e.g., magnetic disks;optical disks; random access memory; read only memory; flash memorydevices; phase-change memory) and machine-readable communication media(e.g., electrical, optical, acoustical or other form of propagatedsignals—such as carrier waves, infrared signals, digital signals, etc.).In addition, such computing devices typically include a set of one ormore processors coupled to one or more other components, such as one ormore storage devices, user input/output devices (e.g., a keyboard, atouchscreen, and/or a display), and network connections. The coupling ofthe set of processors and other components is typically through one ormore busses and bridges (also termed as bus controllers). The storagedevice and signals carrying the network traffic respectively representone or more machine-readable storage media and machine-readablecommunication media. Thus, the storage device of a given computingdevice typically stores code and/or data for execution on the set of oneor more processors of that computing device. Of course, one or moreparts of an embodiment of the invention may be implemented usingdifferent combinations of software, firmware, and/or hardware.

In the preceding description, numerous specific details are set forth.However, it is understood that embodiments may be practiced withoutthese specific details. In other instances, well-known circuits,structures and techniques have not been shown in detail in order not toobscure the understanding of this description. Those of ordinary skillin the art, with the included descriptions, will be able to implementappropriate functionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to affect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

While the flow diagrams in the figures show a particular order ofoperations performed by certain embodiments of the invention, it shouldbe understood that such order is exemplary (e.g., alternativeembodiments may perform the operations in a different order, combinecertain operations, overlap certain operations, etc.).

While the invention has been described in terms of several embodiments,those skilled in the art will recognize that the invention is notlimited to the embodiments described, can be practiced with modificationand alteration within the spirit and scope of the appended claims. Thedescription is thus to be regarded as illustrative instead of limiting.

1. A method, comprising: receiving, at a proxy server, a request for aplurality of content items from a client device, where the proxy serveris in a distributed cloud computing platform; receiving, at the proxyserver, at least one of the plurality of content items from an originserver or a cache; determining, at the proxy server, a priority schemefor ordering the sending of the plurality of content items to the clientdevice, where the priority scheme differs from a priority scheme of theclient device and differs from a priority scheme of a domain of theplurality of content items, and where the priority scheme is acombination of a default priority scheme of the proxy server and apriority scheme provided by the domain of the plurality of contentitems; and sending, by the proxy server, a response including theplurality of content items to the client device in an order according tothe determined priority scheme.
 2. The method of claim 1, furthercomprising: determining priority information provided by a browser ofthe client device.
 3. The method of claim 1, further comprising:determining priority information provided by the domain of the pluralityof content items received from the origin server.
 4. The method of claim1, wherein the determined priority scheme is determined based on acombination of the default priority scheme of the proxy server, thepriority scheme of the domain, and priority information provided by abrowser of the client device.
 5. The method of claim 1, wherein thedetermined priority scheme is determined by utilizing a priority definedby the domain of the plurality of content items in preference to apriority defined by the default priority scheme.
 6. The method of claim1, further comprising: determining a type of each of the plurality ofcontent items; determining a concurrency value; reordering the pluralityof content items with a priority based on respective type of theplurality of content items and the determined priority scheme; andreordering the plurality of content items with a same priority valueaccording to concurrency value, where the plurality of content itemswith a same concurrency value are grouped and share bandwidth.
 7. Themethod of claim 1, wherein the plurality of content items includes anyone of a web page, and image, an audio file, a web application, or ascript.
 8. A non-transitory machine-readable storage medium that storesinstructions, that when executed by a processor of a first server,causes said processor to perform the operations comprising: receiving,at a proxy server, a request for a plurality of content items from aclient device, where the proxy server is in a distributed cloudcomputing platform; receiving, at the proxy server, at least one of theplurality of content items from an origin server or a cache;determining, at the proxy server, a priority scheme for ordering thesending of the plurality of content items to the client device, wherethe priority scheme differs from a priority scheme of the client deviceand differs from a priority scheme of a domain of the plurality ofcontent items, and where the priority scheme is a combination of adefault priority scheme of the proxy server and a priority schemeprovided by the domain of the plurality of content items; and sending,by the proxy server, a response including the plurality of content itemsto the client device in an order according to the determined priorityscheme.
 9. The non-transitory machine-readable storage medium of claim8, wherein the operations further comprise: determining priorityinformation provided by a browser of the client device.
 10. Thenon-transitory machine-readable storage medium of claim 8, wherein theoperations further comprise: determining priority information providedby the domain of the plurality of content items received from the originserver.
 11. The non-transitory machine-readable storage medium of claim8, wherein the determined priority scheme is determined based on acombination of the default priority scheme of the proxy server, thepriority scheme of the domain, and priority information provided by abrowser of the client.
 12. The non-transitory machine-readable storagemedium of claim 8, wherein the determined priority scheme is determinedby utilizing a priority defined by the domain of the plurality ofcontent items in preference to a priority defined by the defaultpriority scheme.
 13. The non-transitory machine-readable storage mediumof claim 8, wherein the operations further comprise: determining a typeof each of the plurality of content items; determining a concurrencyvalue; reordering the plurality of content items with a priority basedon respective type of the plurality of content items and the determinedpriority scheme; and reordering the plurality of content items with asame priority value according to concurrency value, where the pluralityof content items with a same concurrency value are grouped and sharebandwidth.
 14. The non-transitory machine-readable storage medium ofclaim 8, wherein the plurality of content items include any one of a webpage, and image, an audio file, a web application, or a script.
 15. Afirst server, comprising: a processor; and a non-transitorymachine-readable storage medium that provides instructions that, whenexecuted by the processor, causes the first server to perform operationsincluding: receive a request for a plurality of content items from aclient device, where the proxy server is in a distributed cloudcomputing platform; receive at least one of the plurality of contentitems from an origin server or a cache; determine a priority scheme forordering the sending of the plurality of content items to the clientdevice, where the priority scheme differs from a priority scheme of theclient device and differs from a priority scheme of a domain of theplurality of content items, and where the priority scheme is acombination of a default priority scheme of the proxy server and apriority scheme provided by the domain of the plurality of contentitems; and send a response including the plurality of content items tothe client device in an order according to the determined priorityscheme.
 16. The first server of claim 15, wherein the processor isfurther to perform operations comprising: determine priority informationprovided by a browser of the client device.
 17. The first server ofclaim 15, wherein the processor is further to perform operationscomprising: determine priority information provided by the domain of theplurality of content items received from the origin server.
 18. Thefirst server of claim 15, wherein the determined priority scheme isdetermined based on a combination of the default priority scheme of theproxy server, the priority scheme of the domain, and priorityinformation provided by a browser of the client device.
 19. The firstserver of claim 15, wherein the determined priority scheme is determinedby utilizing a priority defined by the domain of the plurality ofcontent items in preference to a priority defined by the defaultpriority scheme.
 20. The first server of claim 15, wherein theoperations further comprise: determine a type of each of the pluralityof content items; determining a concurrency value; reorder the pluralityof content items with a priority based on respective type of theplurality of content items and the determined priority scheme; andreordering the plurality of content items with a same priority valueaccording to concurrency value, where the plurality of content itemswith a same concurrency value are grouped and share bandwidth.
 21. Thefirst server of claim 15, wherein the plurality of content items includeany one of a web page, and image, an audio file, a web application, or ascript.